Built In Searches

1.      Gets All DCs

2.      Selects all DCs for searching

3.      Selects the FRS Log

4.      Selects Error and Warning Events

5.      Sets the Specific IDs to 13520 13560 13561 13514

6.      Gets All DCs

7.      Selects all DCs for searching

8.      Selects the FRS Log

9.      Selects Warning Events

10.  Sets the Specific IDs to 13522

1.      Gets All DCs

2.      Selects all DCs for searching

3.      Selects the FRS Log

4.      Selects Warning Events

5.      Sets the Specific IDs to 13508 and 13509

 

This search also displays and additional dialog box:

 

<<TO DO GET SCREENSHOT>>

 

On this dialog box you can choose which FRS tests to run, the first test is always run. (The slider)

The first test (slider) is always run with this test, it attempts to match 13508s and 13509s, and display and error in the log file if the time difference is more than the number of minute you chose.

Default is 60 minutes (one hour.)

 

            Test Failed Servers for Connectivity, SYSVOL and NETLOGON

                        Calls NetShareEnum and enters into the log if the SYSVOL and

NETLOGON share were found.

                        Default: Enabled

 

Test Failed Servers DNS A Record

            Connects to your default DNS server (bypassing the cache) and prints the

returned address in the log.

Default: Enabled

 

Test Failed Servers for ServerReference

Connects to the PDC and displays its ServerReference attribute for the

failing server, flags an error if the SR attrib doesnÆt contain the ServerName.

Also displays the SR attrib from the server having trouble connecting, and

compares it to the SR attrib on the PDC. Flags an error if they do

not  match.

Default: Enabled

 

Test Failed Servers for RPC connectivity (and Get Polling Intervals)

                        Connects to the FRS RPC service listed as having not replicated. This

                                    verifies name resolution, connectivity, RPC health, and FRS

                                    service status on the remote machine. If successful displays the

                                    Polling Intervals from  the remote server.

                        Default: Enabled

 

            Provide Verbose FRS information on each Domain Controller (50k of text)

                        Dumps lots of data on each FRS config on each machine. Click here to see an example.

 

After choosing RFS health tests, the following dialog is displayed.

 

 

 

All other searches write to an individual log file, however the FRS Health write to a

single file which must be coordinated. The threads must wait for this resource and that can cause the application to appear hung. This is complicated by the fact that some of the calls made by these tests take a long time to fail if the server is unavailable. In particular are NetShareEnum and The RPC binding calls. RPC takes up to a minute (or more) to fail if the server is not available.

The status list box will display the following information when trying these tests so that you can tell it isnÆt hung.

 

 

The FRS report is saved to a file called: FRS_Health_Analysis.txt in the logs directory. Click here to see an example file along with explanation.